Systems and Methods for an Electronic Wallet Payment Tool

ABSTRACT

The systems may include transmitting wallet provider script to a payment service provider server, presenting an electronic wallet payment tool on a merchant checkout page, receiving a first selection of the electronic wallet payment tool, retrieving an electronic wallet comprised in a transaction account associated with the consumer, transmitting transaction account information associated with a desired transaction account in the electronic wallet to the payment service provider server, receiving a virtual token from the payment service provider server, and/or transmitting the virtual token to payment service provider script integrated in a browser used by the consumer.

FIELD

The present disclosure generally relates to systems and methods for an electronic wallet payment tool.

BACKGROUND

A consumer may initiate and complete transactions with a merchant or other party through an online portal. To complete the transactions using an electronic wallet, the consumer may be required to provide personal information or transaction account information to initiate the payment process. Backend transfer of information between the merchant, a payment service provider, the digital wallet, the browser, and/or any other systems or servers may take place in order to complete the transaction, so the information may have some exposure risks.

SUMMARY

A system, method, and article of manufacture (collectively, “the system”) are disclosed relating to an electronic wallet payment tool. In various embodiments, the system may be configured to perform operations including transmitting wallet provider script to a payment service provider server, wherein the payment service provider server is configured to integrate the wallet provider script; presenting an electronic wallet payment tool on a merchant checkout page in response to the transmitting the wallet provider script, the merchant checkout page being part of a merchant server belonging to a merchant, wherein the payment service provider server is integrated with the merchant server; receiving a first selection of the electronic wallet payment tool by a consumer to complete a transaction; retrieving an electronic wallet comprised in a transaction account associated with the consumer, the electronic wallet comprising transaction account information associated with the consumer; transmitting the transaction account information associated with a desired transaction account to the payment service provider server; receiving a virtual token from the payment service provider in response to transmitting the transaction account information; and/or transmitting the virtual token to payment service provider script integrated in a browser used by the consumer, the payment service provider script being configured to receive the virtual token and provide the virtual token to the merchant server.

In various embodiments, the operations may further comprise presenting a login tool in response to the first selection of the electronic wallet payment tool. The operations may further comprise receiving a consumer credential provided by the consumer through the login tool. The operations may further comprise authenticating the consumer associated with the transaction account in response to the receiving the consumer credential. In various embodiments, the operations may further comprise receiving merchant information associated with the merchant. In various embodiments, the operations may further comprise presenting a transaction account selection tool, wherein the transaction account information may comprise information for a plurality of transaction accounts. The operations may further comprise receiving a second selection of the desired transaction account from the plurality of transaction accounts.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter of the present disclosure is particularly pointed out and distinctly claimed in the concluding portion of the specification. A more complete understanding of the present disclosure, however, may best be obtained by referring to the detailed description and claims when considered in connection with the drawing figures.

FIG. 1 shows an exemplary payment system including an electronic wallet payment tool, in accordance with various embodiments;

FIG. 2 shows an exemplary system for integrating a merchant server, payment service provider server, and/or wallet provider server with one another, in accordance with various embodiments;

FIG. 3 shows a flowchart depicting an exemplary method for integrating a merchant into a payment service provider server and/or a wallet provider server, in accordance with various embodiments;

FIG. 4 shows an exemplary user interface on a merchant checkout page, in accordance with various embodiments;

FIG. 5 shows an exemplary login tool, in accordance with various embodiments;

FIG. 6 shows an exemplary transaction account selection tool, in accordance with various embodiments;

FIG. 7 shows an exemplary payment confirmation page, in accordance with various embodiments; and

FIG. 8 shows a flowchart depicting an exemplary method for using a system including an electronic wallet payment tool, in accordance with various embodiments.

DETAILED DESCRIPTION

The present disclosure generally relates to regulating transactions by receiving and analyzing transaction identification information. The detailed description of various embodiments herein makes reference to the accompanying drawings, which show the exemplary embodiments by way of illustration. While these exemplary embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the disclosure. Thus, the detailed description herein is presented for purposes of illustration only and not of limitation. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented. Moreover, any of the functions or steps may be outsourced to or performed by one or more third parties. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component may include a singular embodiment.

In various embodiments, and with reference to FIG. 1, an exemplary payment system for the use with an electronic wallet payment tool is disclosed. In various embodiments, system 100 may comprise a web client 120, a payment service provider (“PSP”) server 130, a merchant server 140, and/or a wallet provider server 150. All or any subset of components of system 100 may be in communication with one another via a network 180. System 100 may allow integration of payment service provider (“PSP”) server 130, merchant server 140, and/or wallet provider server 150 with one another. In various embodiments, integration may occur by PSP server 130, merchant server 140, and/or wallet provider server 150 transmitting script, which another of the PSP server 130, merchant server 140, and/or wallet provider server 150 may download and/or execute. For example, wallet provider server 150 may transmit wallet provider script via network 180 to PSP server 130 and/or merchant server 140. PSP server 130 and/or merchant server 140 may download and/or execute the wallet provider script from wallet provider server 150, thereby integrating wallet provider server 150 with PSP server 130 and/or merchant server 140. Similarly, as another example, PSP server 130 may transmit PSP script to wallet provider server 150 and/or merchant server 140, and wallet provider server 150 and/or merchant server 140 may download and/or execute the PSP script, thereby integrating PSP server 130 with wallet provider server 150 and/or merchant server 140. Once script from one component of system 100 is integrated into another component of system 100, the two components may communicate and/or interact with and/or through one another. System 100 may be computer based, and may comprise a processor, a tangible non-transitory computer-readable memory, and/or a network interface. Instructions stored on the tangible non-transitory memory may allow system 100 to perform various functions, as described herein.

In various embodiments, web client 120 may incorporate hardware and/or software components. For example, web client 120 may comprise a server appliance running a suitable server operating system (e.g., MICROSOFT INTERNET INFORMATION SERVICES or, “IIS”). Web client 120 may be any device that allows a user to communicate with network 180 (e.g., a personal computer, personal digital assistant (e.g., IPHONE®, BLACKBERRY®), cellular phone, kiosk, and/or the like). Web client 120 may be in communication with PSP server 130, merchant server 140, and/or wallet provider server 150 via network 180. Web client 120 may participate in any or all of the functions performed by PSP server 130, merchant server 140, and/or wallet provider server 150 via network 180.

Web client 120 includes any device (e.g., personal computer) which communicates via any network, for example such as those discussed herein. In various embodiments, web client 120 may comprise and/or run a browser 122, such as MICROSOFT® INTERNET EXPLORER®, MOZILLA® FIREFOX®, GOOGLE® CHROME®, APPLE® Safari, or any other of the myriad software packages available for browsing the internet. For example, browser 122 may communicate with merchant server 140 via network 180 by using Internet browsing software installed in browser 122. Browser 122 may comprise Internet browsing software installed within a computing unit or a system to conduct online transactions and/or communications. These computing units or systems may take the form of a computer or set of computers, although other types of computing units or systems may be used, including laptops, notebooks, tablets, hand held computers, personal digital assistants, set-top boxes, workstations, computer-servers, main frame computers, mini-computers, PC servers, pervasive computers, network sets of computers, personal computers, such as IPADS®, IMACS®, and MACBOOKS®, kiosks, terminals, point of sale (POS) devices and/or terminals, televisions, or any other device capable of receiving data over a network. In various embodiments, browser 122 may be configured to display an electronic channel.

In various embodiments, PSP server 130 may comprise hardware and/or software capable of storing data and/or analyzing information. PSP server 130 may comprise a server appliance running a suitable server operating system (e.g., MICROSOFT INTERNET INFORMATION SERVICES or, “IIS”) and having database software (e.g., ORACLE) installed thereon. PSP server 130 may be in electronic communication with web client 120, merchant server 140, and/or wallet provider server 150. In various embodiments, PSP server 130 may be integrated with browser 122, merchant server 140 and/or wallet provider server 150. In various embodiments, PSP server 130 may comprise software and hardware capable of accepting, receiving, processing, and/or analyzing electronic payment types including those from a credit card, debit card, bank transfer, and/or the like, for example, from merchant server 140 during a transaction with a consumer. In various embodiments, PSP server 130 may comprise a payment generator 132 and/or a payment application program interface (“API”) 133, which are further discussed herein.

In various embodiments, merchant server 140 may incorporate hardware and/or software components. For example, merchant server 140 may comprise a server appliance running a suitable server operating system (e.g., Microsoft Internet Information Services or, “IIS”). Merchant server 140 may be in communication with web client 120, PSP server 130 and/or wallet provider server 150. In various embodiments, merchant server 140 may be integrated with browser 122, PSP server 130, and/or wallet provider server 150. Merchants having merchant servers 140 may integrate with PSP server 130, allowing PSP server 130 to accept and/or process payments for the merchant in response to consumers completing transactions with the merchant. Additionally, merchant server 140 may integrate with wallet provider server 150 to use an electronic wallet 152 comprised in wallet provider server 150. The benefits of electronic wallet 152 are discussed further herein. In various embodiments, merchant server 140 may comprise an online store 142, which consumers may access through browser 122 to purchase goods or services from the merchant.

In various embodiments, wallet provider server 150 may belong to any provider of electronic wallets that may store transaction account(s) and/or transaction account information associated with a consumer. Providers of electronic wallets may include issuing banks that issue transaction accounts (for example, American Express issuing charge accounts). Wallet provider server 150 may comprise hardware and/or software capable of storing data and/or analyzing information. Wallet provider server 150 may comprise a server appliance running a suitable server operating system (e.g., MICROSOFT INTERNET INFORMATION SERVICES or, “IIS”) and having database software (e.g., ORACLE) installed thereon. Wallet provider server 150 may be in electronic communication with web client 120, PSP server 130, and/or merchant server 140. In various embodiments, wallet provider server 150 may be integrated with browser 122, PSP server 130, and/or merchant server 140. Wallet provider server 150 may store one or more transaction accounts associated with respective consumers. The transaction accounts may or may not be issued by the wallet provider server 150. In various embodiments, wallet provider server 150 may store transaction accounts associated with a consumer from multiple transaction account issuers. Wallet provider server 150 may comprise an electronic wallet 152. Electronic wallet 152 may be comprised in a transaction account(s) associated with a consumer, and may store transaction account information associated with one or more transaction accounts (i.e., a credit card, debit card, etc.).

In various embodiments, electronic wallet 152 may comprise software and/or hardware that facilitate individual e-commerce and/or m-commerce transactions. As such, a consumer may use the consumer's electronic wallet 152 from wallet provider server 150 to complete a transaction with a merchant, for example, by selecting a transaction account within electronic wallet 152 to use for payment to complete the transaction. Transactions may be facilitated by electronic wallet 152 aggregating the consumer's payment and/or billing information, serving as the merchant of record, and/or passing through the consumer's payment information, transaction account information, and/or billing information to the merchant. In various embodiments, wallet provider server 150 may receive and store a plurality of transaction accounts with an electronic wallet(s) associated with respective consumers.

In various embodiments, network 180 may be an open network or a closed loop network. The open network may be a network that is accessible by various third parties. In this regard, the open network may be the internet, a typical transaction network, and/or the like. Network 180 may also be a closed network. In this regard, network 180 may be a closed loop network like the network operated by American Express. Moreover, the closed loop network may be configured with enhanced security and monitoring capability. For example, the closed network may be configured with tokenization, associated domain controls, and/or other enhanced security protocols. In this regard, network 180 may be configured to monitor users on network 180. In this regard, the closed loop network may be a secure network and may be an environment that can be monitored, having enhanced security features.

According to various embodiments, FIG. 2 depicts a system 200 for integrating merchant server 140, PSP server 130, and/or wallet provider server 150 with one another. With combined reference to FIGS. 1 and 2, wallet provider server 150 may be integrated into PSP server 130, and PSP server 130 may provide payment API 133 (i.e., a type of PSP script), or any other type of PSP script, to wallet provider server 150 for such integration. Payment API 133 may be customized by PSP server 130 for each distinct wallet provider server 150 and/or electronic wallet 152. In various embodiments, wallet provider server 150 may comprise a merchant onboarding API 154, and may provide merchant onboarding API 154 (i.e., a type of wallet provider script) to PSP server 130. PSP server 130 may invoke merchant onboarding API 154 to onboard (i.e., integrate) a merchant server 140. Merchant server 140 may be integrated into PSP server 130 via a merchant onboarding site 135 comprised in PSP server 130. In response to merchant server 140 being integrated into PSP server 130, merchant server 140 may also be integrated into wallet provider server 150 through merchant onboarding API 154, which is integrated into PSP server 130. Through such integration, merchant server 140 may comprise PSP script and/or wallet provider script.

FIG. 3 depicts a method 300 for integrating a merchant (i.e., a merchant server 140) with a PSP server 130 and/or wallet provider server 150, in accordance with various embodiments. With combined reference to FIGS. 1-3, a merchant, which comprises an associated merchant server 140, may access a PSP portal comprised within PSP server 130 (step 102), which may be a part of merchant onboarding site 135. Step 104 may determine if the merchant is already integrated into PSP server 130 and/or wallet provider server 150. In response to the merchant not being integrated into PSP server 130 and/or wallet provider server 150, the merchant may provide its merchant information (e.g., contact information, acquirer, technological information, etc.) to the PSP portal in PSP server 130 (step 108). In response to the merchant already being integrated into PSP server 130 and/or wallet provider server 150, the merchant may update its merchant information to the PSP portal in PSP server 130. PSP server 130 may transmit the new and/or updated merchant information to wallet provider server 150 (step 110). Such transmission may be via merchant onboarding API 154, and/or any other wallet provider script transmitted and hosted by wallet provider server 150, that is integrated into PSP server 130.

With reference to FIGS. 1 and 4-7, in response to a merchant being integrated with wallet provider server 150, the merchant may utilize electronic wallet 152 through an electronic wallet payment tool on online store 142 to facilitate transactions. A consumer may shop on online store 142, and in response to being ready to pay for any goods and/or services selected, the consumer may access merchant checkout page 302. Merchant checkout page 302 may list transaction information such as the goods and/or services to be purchased (e.g., a mountain bike), the price, and/or any additional fees or costs. To complete the transaction, the consumer may be requested to enter his or her consumer information in consumer information box 304. For example, a consumer may be requested to provide a full name, address, phone number, email address, and/or transaction account information, such as credit card or debit card information.

In various embodiments, as discussed herein, the merchant and merchant server 140 may be integrated with wallet provider server 150. Through this integration, wallet provider server 150 may present an electronic wallet payment tool 310 on merchant checkout page 302. The consumer may select electronic wallet payment tool 310, and the consumer may be prompted to enter a consumer credential(s) (e.g., a username and password, a biometric, or any other identifier information associated with the consumer) on a login tool 315 to access the consumer's electronic wallet 152 within wallet provider server 150. Electronic wallet 152 may comprise transaction account information for one or more transaction accounts. In response to the consumer successfully logging into the electronic wallet payment tool 310, wallet provider server 150 may present the consumer with a transaction account selection tool 317 which may list all of the transaction accounts in electronic wallet 152 associated with the consumer for which wallet provider server 150 has transaction account information. In the event that the consumer has one transaction account in electronic wallet 152, wallet provider server 150 may automatically select that transaction account as the selected transaction account for the transaction. In response to the consumer selecting a desired transaction account of multiple transaction accounts, wallet provider server 150 may facilitate the transaction by providing the consumer information and/or transaction account information associated with the desired transaction account to the PSP server 130. As a result, the consumer may not be requested to provide all of the consumer information in consumer information box 304. Wallet provider server 150 and/or PSP server 130 may facilitate payment for the transaction, and the consumer may be presented with a payment confirmation page 319 showing the consumer information and/or transaction account information of the desired transaction account as provided by the wallet provider server 150.

With respect to FIG. 8, the process flow depicted is merely an embodiment of various embodiments, and is not intended to limit the scope of the disclosure. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented. It will be appreciated that the description herein makes appropriate references not only to the steps and consumer interface elements depicted in FIG. 8, but also to the various system components as described above with reference to FIGS. 1, 2, and 4-7.

In accordance with various embodiments, FIG. 8 depicts a method for using a system including an electronic wallet payment tool. With combined reference to FIGS. 1, 2, and 4-7, a consumer may navigate to merchant checkout page 302 (step 802) located in online store 142 on a merchant server 140. Merchant server 140 may be associated with a specific merchant. The consumer may access online store 142 via browser 122 on web client 120, wherein browser 122 may request merchant checkout page 302 from merchant server 140. The merchant may have provided its merchant information to PSP server 130 and/or wallet provider server 150 via merchant onboarding site 135 and/or merchant onboarding API 154, respectively. Accordingly, merchant server 140 may be integrated into PSP server 130 and/or wallet provider server 150. PSP server 130 may be integrated with wallet provider server 150.

In various embodiments, browser 122 may download PSP script (step 804) provided by PSP server 130. In response, PSP server 130 and browser 122 may be integrated. PSP server 130 and/or the PSP script comprised in browser 122 may download and/or execute wallet provider script (step 806), the wallet provider script being transmitted by wallet provider server 150. Accordingly, the PSP script in browser 122 may comprise wallet provider script. In response to the PSP script comprised in browser 122 downloading and/or executing wallet provider script, an electronic wallet payment tool 310 may be presented on merchant checkout page 302 (step 808). Electronic wallet payment tool 310 may be in the form of an electronic (software-enabled) button, which a consumer may press with their finger, a mouse, or any other selection device, to select electronic wallet payment tool 310 (step 810). In response to selecting electronic wallet payment tool 310, the consumer may be presented with a login tool 315 (step 812) requesting a consumer credential(s). Login tool 315 may be presented by browser 122, PSP server 130, merchant server 140, and/or wallet provider server 150. The consumer may input the consumer credential(s), which may be received by browser 122, PSP server 130, merchant server 140, and/or wallet provider server 150 (step 814).

In various embodiments, wallet provider server 150 may receive the consumer credential(s). Wallet provider server 150 may compare the consumer credential(s) provided by the consumer with stored consumer credential(s) associated with specific transaction accounts. In response to the consumer credential(s) matching the stored consumer credential(s) associated with a transaction account(s), wallet provider server 150 may authenticate the consumer (step 816). In response to the consumer being authenticated, wallet provider server 150 may retrieve from its own backend (i.e., from the information stored within wallet provider server 150) transaction account information for transaction account(s) associated with the consumer (step 818). The transaction account(s) may be stored in and/or associated with an electronic wallet 152. In response to there being multiple transaction accounts within electronic wallet 152, a transaction account selection tool 317 may be presented by the web client 120, browser 122, PSP server 130, merchant server 140, and/or wallet provider server 150. The consumer may select a desired transaction account from transaction account selection tool 317. The selection may be received by wallet provider server 150 and/or PSP server 130 (step 820).

In various embodiments, in response to a transaction account(s) being identified, the desired transaction account being selected, and the selection being received by wallet provider server 150, wallet provider server 150 may transmit the transaction account information associated with the desired transaction account to PSP server 130 (step 822), which may be via payment API 133. In response, PSP server 130 may generate a virtual token via payment generator 132. The virtual token may be an identifier, specific to a certain transaction, of the transaction account with which the transaction account information is associated. PSP server 130 may transmit the virtual token to wallet provider server 150 (step 824). The virtual token then may act as a payment device for the transaction account within electronic wallet 152 in wallet provider server 150. Wallet provider server 150 may transmit the virtual token to browser 122 and/or the wallet provider script integrated in browser 122 (step 826). The wallet provider script in browser 122 may transmit the virtual token to the PSP script, in which the wallet provider script is comprised, in browser 122 (step 828). The PSP script integrated in browser 122 may receive the virtual token and transmit it to the online store 142 on the merchant server 140 (step 830). In response to merchant server 140 receiving the virtual token, the transaction with the consumer may be completed by merchant server 140 presenting the virtual token to PSP server 130, and PSP server 130 sending a confirmation to merchant server 140, such as a credit to the merchant. The consumer may receive payment confirmation page 319.

With reference to FIGS. 1, 2, and 4-7, in various embodiments, system 100 simplifies the payment process for the transaction between a consumer and a merchant. As described herein, system 100 does not require the consumer to input any consumer information or transaction account information on merchant checkout page 302. The integration of wallet provider server 150, including electronic wallet 152, with browser 122, merchant server 140, and/or PSP server 130 requires only that the consumer select electronic wallet payment tool 310 and provide a consumer credential(s) to login tool 315. Wallet provider server 150 may provide the consumer information and/or transaction account information, which wallet provider server 150 already has stored, to PSP server 130, merchant server 140, and/or browser 122. Additionally, as described herein, browser 122 may be integrated with PSP server 130 and/or wallet provider server 150, and PSP server 130, merchant server 140, and/or wallet provider server 150 may be integrated with one another. Such integration may streamline the payment process in response to a consumer initiating a transaction with a merchant.

Accordingly, with reference to FIG. 8, wallet provider server 150 transmitting the transaction account information to PSP server 130 (step 822), PSP server 130 transmitting a virtual token to wallet provider server 150 (step 824), wallet provider server 150 transmitting the virtual token to the wallet provider script in browser 122 (step 826), and/or the wallet provider script transmitting the virtual token to the PSP script integrated into browser 122 (step 828) may all take place as if occurring in the same component of system 100 (i.e., PSP server 130) because the components are integrated. Therefore, merchant server 140 may receive the virtual token seemingly from only one source (i.e., PSP server 130), making the transaction process through system 100 easier and faster for the consumer and all other involved parties.

The various components in system 100 may be independently, separately or collectively suitably coupled to each other, and/or network 180, via data links which include, for example, a connection to an Internet Service Provider (ISP) over the local loop as is typically used in connection with standard modem communication, cable modem, Dish Networks®, ISDN, Digital Subscriber Line (DSL), or various wireless communication methods, see, e.g., GILBERT HELD, UNDERSTANDING DATA COMMUNICATIONS (1996), which is hereby incorporated by reference. It is noted that the network may be implemented as other types of networks, such as an interactive television (ITV) network. Moreover, the system contemplates the use, sale or distribution of any goods, services or information over any network having similar functionality described herein.

In various embodiments, the system and method may include alerting a subscriber (e.g., a user, consumer, etc.) when their web client 120 (e.g., computer) is offline. The system may include generating customized information and alerting a remote subscriber that the information can be accessed from their computer. The alerts are generated by filtering received information, building information alerts and formatting the alerts into data blocks based upon subscriber preference information. The data blocks are transmitted to the subscriber's wireless device which, when connected to the computer, causes the computer to auto-launch an application to display the information alert and provide access to more detailed information about the information alert. More particularly, the method may comprise providing a viewer application to a subscriber for installation on the remote subscriber computer; receiving information at a transmission server sent from a data source over the Internet, the transmission server comprising a microprocessor and a memory that stores the remote subscriber's preferences for information format, destination address, specified information, and transmission schedule, wherein the microprocessor filters the received information by comparing the received information to the specified information; generates an information alert from the filtered information that contains a name, a price and a universal resource locator (URL), which specifies the location of the data source; formats the information alert into data blocks according to said information format; and transmits the formatted information alert over a wireless communication channel to a wireless device associated with a subscriber based upon the destination address and transmission schedule, wherein the alert activates the application to cause the information alert to display on the remote subscriber computer and to enable connection via the URL to the data source over the Internet when the wireless device is locally connected to the remote subscriber computer and the remote subscriber computer comes online.

In various embodiments, the system and method may include a graphical user interface (i.e., comprised in web client 120) for dynamically relocating/rescaling obscured textual information of an underlying window to become automatically viewable to the user. Such textual information may be comprised in merchant checkout page 302, login tool 315, transaction account selection tool 317, payment confirmation page 319, and/or any other interface presented to the consumer or user. By permitting textual information to be dynamically relocated based on an overlap condition, the computer's ability to display information is improved. More particularly, the method for dynamically relocating textual information within an underlying window displayed in a graphical user interface may comprise displaying a first window containing textual information in a first format within a graphical user interface on a computer screen (comprised in web client 120, for example); displaying a second window within the graphical user interface; constantly monitoring the boundaries of the first window and the second window to detect an overlap condition where the second window overlaps the first window such that the textual information in the first window is obscured from a user's view; determining the textual information would not be completely viewable if relocated to an unobstructed portion of the first window; calculating a first measure of the area of the first window and a second measure of the area of the unobstructed portion of the first window; calculating a scaling factor which is proportional to the difference between the first measure and the second measure; scaling the textual information based upon the scaling factor; automatically relocating the scaled textual information, by a processor, to the unobscured portion of the first window in a second format during an overlap condition so that the entire scaled textual information is viewable on the computer screen by the user; and automatically returning the relocated scaled textual information, by the processor, to the first format within the first window when the overlap condition no longer exists.

In various embodiments, the system may also include isolating and removing malicious code from electronic messages (e.g., email, messages within online store 142) to prevent a computer, server, and/or system from being compromised, for example by being infected with a computer virus. The system may scan electronic communications for malicious computer code and clean the electronic communication before it may initiate malicious acts. The system operates by physically isolating a received electronic communication in a “quarantine” sector of the computer memory. A quarantine sector is a memory sector created by the computer's operating system such that files stored in that sector are not permitted to act on files outside that sector. When a communication containing malicious code is stored in the quarantine sector, the data contained within the communication is compared to malicious code-indicative patterns stored within a signature database. The presence of a particular malicious code-indicative pattern indicates the nature of the malicious code. The signature database further includes code markers that represent the beginning and end points of the malicious code. The malicious code is then extracted from malicious code-containing communication. An extraction routine is run by a file parsing component of the processing unit. The file parsing routine performs the following operations: scan the communication for the identified beginning malicious code marker; flag each scanned byte between the beginning marker and the successive end malicious code marker; continue scanning until no further beginning malicious code marker is found; and create a new data file by sequentially copying all non-flagged data bytes into the new file, which thus forms a sanitized communication file. The new, sanitized communication is transferred to a non-quarantine sector of the computer memory. Subsequently, all data on the quarantine sector is erased. More particularly, the system includes a method for protecting a computer from an electronic communication containing malicious code by receiving an electronic communication containing malicious code in a computer with a memory having a boot sector, a quarantine sector and a non-quarantine sector; storing the communication in the quarantine sector of the memory of the computer, wherein the quarantine sector is isolated from the boot and the non-quarantine sector in the computer memory, where code in the quarantine sector is prevented from performing write actions on other memory sectors; extracting, via file parsing, the malicious code from the electronic communication to create a sanitized electronic communication, wherein the extracting comprises scanning the communication for an identified beginning malicious code marker, flagging each scanned byte between the beginning marker and a successive end malicious code marker, continuing scanning until no further beginning malicious code marker is found, and creating a new data file by sequentially copying all non-flagged data bytes into a new file that forms a sanitized communication file; transferring the sanitized electronic communication to the non-quarantine sector of the memory; and deleting all data remaining in the quarantine sector.

In various embodiments, the system may also address the problem of retaining control over consumers during affiliate purchase transactions, using a system for co-marketing the “look and feel” of the host web page (e.g., online store 142) with the product-related content information of the advertising merchant's web page. The system can be operated by a third-party outsource provider, who acts as a broker between multiple hosts and advertising merchants. Prior to implementation, a host places links to an advertising merchant's server on the host's web page (e.g., online store 142). The links are associated with product-related content on the advertising merchant's web page. Additionally, the outsource provider system stores the “look and feel” information from each host's web pages in a computer data store, which is coupled to a computer server. The “look and feel” information includes visually perceptible elements such as logos, colors, page layout, navigation system, frames, mouse-over effects or other elements that are consistent through some or all of each host's respective web pages. A consumer who clicks on an advertising link is not transported from the host web page to the advertising merchant's web page, but instead is re-directed to a composite web page that combines product information associated with the selected item and visually perceptible elements of the host web page. The outsource provider's server responds by first identifying the host web page where the link has been selected and retrieving the corresponding stored “look and feel” information. The server constructs a composite web page using the retrieved “look and feel” information of the host web page, with the product-related content embedded within it, so that the composite web page is visually perceived by the consumer as associated with the host web page. The server then transmits and presents this composite web page to the consumer so that she effectively remains on the host web page to purchase the item without being redirected to the third party advertising merchant affiliate. Because such composite pages are visually perceived by the consumer as associated with the host web page, they give the consumer the impression that she is viewing pages served by the host. Further, the consumer is able to purchase the item without being redirected to the third party advertising merchant affiliate, thus allowing the host to retain control over the consumer. This system enables the host to receive the same advertising revenue streams as before but without the loss of visitor traffic and potential customers. More particularly, the system may be useful in an outsource provider serving web pages offering commercial opportunities. The computer store containing data, for each of a plurality of first web pages, defining a plurality of visually perceptible elements, which visually perceptible elements correspond to the plurality of first web pages; wherein each of the first web pages belongs to one of a plurality of web page owners; wherein each of the first web pages displays at least one active link associated with a commerce object associated with a buying opportunity of a selected one of a plurality of advertising merchants; and wherein the selected advertising merchant, the outsource provider, and the owner of the first web page displaying the associated link are each third parties with respect to one other; a computer server at the outsource provider, which computer server is coupled to the computer store and programmed to: receive from the web browser of a computer user a signal indicating activation of one of the links displayed by one of the first web pages; automatically identify as the source page the one of the first web pages on which the link has been activated; in response to identification of the source page, automatically retrieve the stored data corresponding to the source page; and using the data retrieved, automatically generate and transmit to the web browser a second web page that displays: information associated with the commerce object associated with the link that has been activated, and the plurality of visually perceptible elements visually corresponding to the source page.

Systems, methods and computer program products are provided. In the detailed description herein, references to “various embodiments”, “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. After reading the description, it will be apparent to one skilled in the relevant art(s) how to implement the disclosure in alternative embodiments.

As used herein, “satisfy”, “meet”, “match”, “associated with” or similar phrases may include an identical match, a partial match, meeting certain criteria, matching a subset of data, a correlation, satisfying certain criteria, a correspondence, an association, an algorithmic relationship and/or the like. Similarly, as used herein, “authenticate” or similar terms may include an exact authentication, a partial authentication, authenticating a subset of data, a correspondence, satisfying certain criteria, an association, an algorithmic relationship and/or the like.

Terms and phrases similar to “associate” and/or “associating” may include tagging, flagging, correlating, using a look-up table or any other method or system for indicating or creating a relationship between elements, such as, for example, (i) a transaction account, (ii) an electronic wallet, and/or (iii) a consumer. Moreover, the associating may occur at any point, in response to any suitable action, event, or period of time. The associating may occur at pre-determined intervals, periodic, randomly, once, more than once, or in response to a suitable request or action. Any of the information may be distributed and/or accessed via a software enabled link, wherein the link may be sent via an email, text, post, social network input and/or any other method known in the art.

The phrases consumer, customer, user, account holder, account affiliate, cardmember or the like shall include any person, entity, business, government organization, business, software, hardware, machine associated with a transaction account, which buys merchant offerings offered by one or more merchants using the account and/or who is legally designated for performing transactions on the account, regardless of whether a physical card is associated with the account. For example, the cardmember may include a transaction account owner, a transaction account user, an account affiliate, a child account user, a subsidiary account user, a beneficiary of an account, a custodian of an account, and/or any other person or entity affiliated or associated with a transaction account.

As used herein, big data may refer to partially or fully structured, semi-structured, or unstructured data sets including millions of rows and hundreds of thousands of columns. A big data set may be compiled, for example, from a history of purchase transactions over time, from web registrations, from social media, from records of charge (ROC), from summaries of charges (SOC), from internal data, or from other suitable sources. Big data sets may be compiled without descriptive metadata such as column types, counts, percentiles, or other interpretive-aid data points.

Distributed computing cluster may be, for example, a Hadoop® cluster configured to process and store big data sets with some of nodes comprising a distributed storage system and some of nodes comprising a distributed processing system. In that regard, distributed computing cluster may be configured to support a Hadoop® distributed file system (HDFS) as specified by the Apache Software Foundation at http://hadoop.apache.org/docs/. For more information on big data management systems, see U.S. Ser. No. 14/944,902 titled INTEGRATED BIG DATA INTERFACE FOR MULTIPLE STORAGE TYPES and filed on Nov. 18, 2015; U.S. Ser. No. 14/944,979 titled SYSTEM AND METHOD FOR READING AND WRITING TO BIG DATA STORAGE FORMATS and filed on Nov. 18, 2015; U.S. Ser. No. 14/945,032 titled SYSTEM AND METHOD FOR CREATING, TRACKING, AND MAINTAINING BIG DATA USE CASES and filed on Nov. 18, 2015; U.S. Ser. No. 14/944,849 titled SYSTEM AND METHOD FOR AUTOMATICALLY CAPTURING AND RECORDING LINEAGE DATA FOR BIG DATA RECORDS and filed on Nov. 18, 2015; U.S. Ser. No. 14/944,898 titled SYSTEMS AND METHODS FOR TRACKING SENSITIVE DATA IN A BIG DATA ENVIRONMENT and filed on Nov. 18, 2015; and U.S. Ser. No. 14/944,961 titled SYSTEM AND METHOD TRANSFORMING SOURCE DATA INTO OUTPUT DATA IN BIG DATA ENVIRONMENTS and filed on Nov. 18, 2015, the contents of each of which are herein incorporated by reference in their entirety.

Any communication, transmission and/or channel discussed herein may include any system or method for delivering content (e.g. data, information, metadata, etc), and/or the content itself. The content may be presented in any form or medium, and in various embodiments, the content may be delivered electronically and/or capable of being presented electronically. For example, a channel may comprise a website or device (e.g., Facebook, YOUTUBE®, APPLE®TV®, PANDORA®, XBOX®, SONY® PLAYSTATION®), a uniform resource locator (“URL”), a document (e.g., a MICROSOFT® Word® document, a MICROSOFT® Excel® document, an ADOBE® .pdf document, etc.), an “ebook,” an “emagazine,” an application or microapplication (as described herein), an SMS or other type of text message, an email, facebook, twitter, MMS and/or other type of communication technology. In various embodiments, a channel may be hosted or provided by a data partner. In various embodiments, the distribution channel may comprise at least one of a merchant website, a social media website, affiliate or partner websites, an external vendor, a mobile device communication, social media network and/or location based service. Distribution channels may include at least one of a merchant website, a social media site, affiliate or partner websites, an external vendor, and a mobile device communication. Examples of social media sites include FACEBOOK®, FOURSQUARE®, TWITTER®, MYSPACE®, LINKEDIN®, and the like. Examples of affiliate or partner websites include AMERICAN EXPRESS®, GROUPON®, LIVINGSOCIAL®, and the like. Moreover, examples of mobile device communications include texting, email, and mobile applications for smartphones.

A “consumer profile” or “consumer profile data” may comprise any information or data about a consumer that describes an attribute associated with the consumer (e.g., a preference, an interest, demographic information, personally identifying information, and the like).

In various embodiments, the methods described herein are implemented using the various particular machines described herein. The methods described herein may be implemented using the below particular machines, and those hereinafter developed, in any suitable combination, as would be appreciated immediately by one skilled in the art. Further, as is unambiguous from this disclosure, the methods described herein may result in various transformations of certain articles.

For the sake of brevity, conventional data networking, application development and other functional aspects of the systems (and components of the individual operating components of the systems) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical system.

The various system components discussed herein may include one or more of the following: a host server or other computing systems including a processor for processing digital data; a memory coupled to the processor for storing digital data; an input digitizer coupled to the processor for inputting digital data; an application program stored in the memory and accessible by the processor for directing processing of digital data by the processor; a display device coupled to the processor and memory for displaying information derived from digital data processed by the processor; and a plurality of databases. Various databases used herein may include: client data; merchant data; financial institution data; and/or like data useful in the operation of the system. As those skilled in the art will appreciate, user computer may include an operating system (e.g., WINDOWS®, OS2, UNIX®, LINUX®, SOLARIS®, MacOS, etc.) as well as various conventional support software and drivers typically associated with computers.

The present system or any part(s) or function(s) thereof may be implemented using hardware, software or a combination thereof and may be implemented in one or more computer systems or other processing systems. However, the manipulations performed by embodiments were often referred to in terms, such as matching or selecting, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein. Rather, the operations may be machine operations. Useful machines for performing the various embodiments include general purpose digital computers or similar devices.

In fact, in various embodiments, the embodiments are directed toward one or more computer systems capable of carrying out the functionality described herein. The computer system includes one or more processors, such as processor. The processor is connected to a communication infrastructure (e.g., a communications bus, cross-over bar, or network). Various software embodiments are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the relevant art(s) how to implement various embodiments using other computer systems and/or architectures. Computer system can include a display interface that forwards graphics, text, and other data from the communication infrastructure (or from a frame buffer not shown) for display on a display unit.

Computer system also includes a main memory, such as for example random access memory (RAM), and may also include a secondary memory. The secondary memory may include, for example, a hard disk drive and/or a removable storage drive, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive reads from and/or writes to a removable storage unit in a well-known manner. Removable storage unit represents a floppy disk, magnetic tape, optical disk, etc. which is read by and written to by removable storage drive. As will be appreciated, the removable storage unit includes a computer usable storage medium having stored therein computer software and/or data.

In various embodiments, secondary memory may include other similar devices for allowing computer programs or other instructions to be loaded into computer system. Such devices may include, for example, a removable storage unit and an interface. Examples of such may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an erasable programmable read only memory (EPROM), or programmable read only memory (PROM)) and associated socket, and other removable storage units and interfaces, which allow software and data to be transferred from the removable storage unit to computer system.

Computer system may also include a communications interface. Communications interface allows software and data to be transferred between computer system and external devices. Examples of communications interface may include a modem, a network interface (such as an Ethernet card), a communications port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, etc. Software and data transferred via communications interface are in the form of signals which may be electronic, electromagnetic, optical or other signals capable of being received by communications interface. These signals are provided to communications interface via a communications path (e.g., channel). This channel carries signals and may be implemented using wire, cable, fiber optics, a telephone line, a cellular link, a radio frequency (RF) link, wireless and other communications channels.

The terms “computer program medium” and “computer usable medium” and “computer readable medium” are used to generally refer to media such as removable storage drive and a hard disk installed in hard disk drive. These computer program products provide software to computer system.

Computer programs (also referred to as computer control logic) are stored in main memory and/or secondary memory. Computer programs may also be received via communications interface. Such computer programs, when executed, enable the computer system to perform the features as discussed herein. In particular, the computer programs, when executed, enable the processor to perform the features of various embodiments. Accordingly, such computer programs represent controllers of the computer system.

In various embodiments, software may be stored in a computer program product and loaded into computer system using removable storage drive, hard disk drive or communications interface. The control logic (software), when executed by the processor, causes the processor to perform the functions of various embodiments as described herein. In various embodiments, hardware components such as application specific integrated circuits (ASICs). Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s).

Practitioners will appreciate that web client 120 may or may not be in direct contact with an application server. For example, web client 120 may access the services of an application server through another server and/or hardware component, which may have a direct or indirect connection to an Internet server. For example, web client 120 may communicate with an application server via a load balancer. In various embodiments, access is through a network or the Internet through a commercially-available web-browser software package.

As those skilled in the art will appreciate, web client 120 may include an operating system (e.g., WINDOWS®/CE/Mobile, OS2, UNIX®, LINUX®, SOLARIS®, MacOS, etc.) as well as various conventional support software and drivers typically associated with computers. Web client 120 may include any suitable personal computer, network computer, workstation, personal digital assistant, cellular phone, smart phone, minicomputer, mainframe or the like. Web client 120 can be in a home or business environment with access to a network. In various embodiments, access is through a network or the Internet through a commercially available web-browser software package. Web client 120 may implement security protocols such as Secure Sockets Layer (SSL) and Transport Layer Security (TLS). Web client 120 may implement several application layer protocols including http, https, ftp, and sftp.

As used herein, the term “network” includes any cloud, cloud computing system or electronic communications system or method which incorporates hardware and/or software components. Communication among the parties may be accomplished through any suitable communication channels, such as, for example, a telephone network, an extranet, an intranet, Internet, point of interaction device (point of sale device, personal digital assistant (e.g., IPHONE®, BLACKBERRY®), cellular phone, kiosk, etc.), online communications, satellite communications, off-line communications, wireless communications, transponder communications, local area network (LAN), wide area network (WAN), virtual private network (VPN), networked or linked devices, keyboard, mouse and/or any suitable communication or data input modality. Moreover, although the system is frequently described herein as being implemented with TCP/IP communications protocols, the system may also be implemented using IPX, APPLE®talk, IP-6, NetBIOS®, OSI, any tunneling protocol (e.g. IPsec, SSH), or any number of existing or future protocols. If the network is in the nature of a public network, such as the Internet, it may be advantageous to presume the network to be insecure and open to eavesdroppers. Specific information related to the protocols, standards, and application software utilized in connection with the Internet is generally known to those skilled in the art and, as such, need not be detailed herein. See, for example, DILIP NAIK, INTERNET STANDARDS AND PROTOCOLS (1998); JAVA® 2 COMPLETE, various authors, (Sybex 1999); DEBORAH RAY AND ERIC RAY, MASTERING HTML 4.0 (1997); and LOSHIN, TCP/IP CLEARLY EXPLAINED (1997) and DAVID GOURLEY AND BRIAN TOTTY, HTTP, THE DEFINITIVE GUIDE (2002), the contents of which are hereby incorporated by reference.

“Cloud” or “Cloud computing” includes a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. Cloud computing may include location-independent computing, whereby shared servers provide resources, software, and data to computers and other devices on demand. For more information regarding cloud computing, see the NIST's (National Institute of Standards and Technology) definition of cloud computing at http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf (last visited June 2012), which is hereby incorporated by reference in its entirety.

As used herein, “transmit” may include sending electronic data from one system component to another over a network connection. Additionally, as used herein, “data” may include encompassing information such as commands, queries, files, data for storage, and the like in digital or any other form.

Phrases and terms similar to an “item” may include any good, service, information, experience, entertainment, data, offer, discount, rebate, points, virtual currency, content, access, rental, lease, contribution, account, credit, debit, benefit, right, reward, points, coupons, credits, monetary equivalent, anything of value, something of minimal or no value, monetary value, non-monetary value and/or the like. Moreover, the “transactions” or “purchases” discussed herein may be associated with an item. Furthermore, a “reward” may be an item.

The system contemplates uses in association with web services, utility computing, pervasive and individualized computing, security and identity solutions, autonomic computing, cloud computing, commodity computing, mobility and wireless solutions, open source, biometrics, grid computing and/or mesh computing.

Any databases discussed herein may include relational, hierarchical, graphical, or object-oriented structure and/or any other database configurations. Common database products that may be used to implement the databases include DB2 by IBM® (Armonk, N.Y.), various database products available from ORACLE® Corporation (Redwood Shores, Calif.), MICROSOFT® Access® or MICROSOFT® SQL Server® by MICROSOFT® Corporation (Redmond, Wash.), MySQL by MySQL AB (Uppsala, Sweden), or any other suitable database product. Moreover, the databases may be organized in any suitable manner, for example, as data tables or lookup tables. Each record may be a single file, a series of files, a linked series of data fields or any other data structure. Association of certain data may be accomplished through any desired data association technique such as those known or practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, using a key field in the tables to speed searches, sequential searches through all the tables and files, sorting records in the file according to a known order to simplify lookup, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in pre-selected databases or data sectors. Various database tuning steps are contemplated to optimize database performance. For example, frequently used files such as indexes may be placed on separate file systems to reduce In/Out (“I/O”) bottlenecks.

More particularly, a “key field” partitions the database according to the high-level class of objects defined by the key field. For example, certain types of data may be designated as a key field in a plurality of related data tables and the data tables may then be linked on the basis of the type of data in the key field. The data corresponding to the key field in each of the linked data tables is preferably the same or of the same type. However, data tables having similar, though not identical, data in the key fields may also be linked by using AGREP, for example. In accordance with one embodiment, any suitable data storage technique may be utilized to store data without a standard format. Data sets may be stored using any suitable technique, including, for example, storing individual files using an ISO/IEC 7816-4 file structure; implementing a domain whereby a dedicated file is selected that exposes one or more elementary files containing one or more data sets; using data sets stored in individual files using a hierarchical filing system; data sets stored as records in a single file (including compression, SQL accessible, hashed via one or more keys, numeric, alphabetical by first tuple, etc.); Binary Large Object (BLOB); stored as ungrouped data elements encoded using ISO/IEC 7816-6 data elements; stored as ungrouped data elements encoded using ISO/IEC Abstract Syntax Notation (ASN.1) as in ISO/IEC 8824 and 8825; and/or other proprietary techniques that may include fractal compression methods, image compression methods, etc.

In various embodiments, the ability to store a wide variety of information in different formats is facilitated by storing the information as a BLOB. Thus, any binary information can be stored in a storage space associated with a data set. As discussed above, the binary information may be stored in association with the system or external to but affiliated with system. The BLOB method may store data sets as ungrouped data elements formatted as a block of binary via a fixed memory offset using either fixed storage allocation, circular queue techniques, or best practices with respect to memory management (e.g., paged memory, least recently used, etc.). By using BLOB methods, the ability to store various data sets that have different formats facilitates the storage of data, in the database or associated with the system, by multiple and unrelated owners of the data sets. For example, a first data set which may be stored may be provided by a first party, a second data set which may be stored may be provided by an unrelated second party, and yet a third data set which may be stored, may be provided by an third party unrelated to the first and second party. Each of these three exemplary data sets may contain different information that is stored using different data storage formats and/or techniques. Further, each data set may contain subsets of data that also may be distinct from other subsets.

As stated above, in various embodiments, the data can be stored without regard to a common format. However, the data set (e.g., BLOB) may be annotated in a standard manner when provided for manipulating the data in the database or system. The annotation may comprise a short header, trailer, or other appropriate indicator related to each data set that is configured to convey information useful in managing the various data sets. For example, the annotation may be called a “condition header”, “header”, “trailer”, or “status”, herein, and may comprise an indication of the status of the data set or may include an identifier correlated to a specific issuer or owner of the data. In one example, the first three bytes of each data set BLOB may be configured or configurable to indicate the status of that particular data set; e.g., LOADED, INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED. Subsequent bytes of data may be used to indicate for example, the identity of the issuer, user, transaction/membership account identifier or the like. Each of these condition annotations are further discussed herein.

The data set annotation may also be used for other types of status information as well as various other purposes. For example, the data set annotation may include security information establishing access levels. The access levels may, for example, be configured to permit only certain individuals, levels of employees, companies, or other entities to access data sets, or to permit access to specific data sets based on the transaction, merchant, issuer, user or the like. Furthermore, the security information may restrict/permit only certain actions such as accessing, modifying, and/or deleting data sets. In one example, the data set annotation indicates that only the data set owner or the user are permitted to delete a data set, various identified users may be permitted to access the data set for reading, and others are altogether excluded from accessing the data set. However, other access restriction parameters may also be used allowing various entities to access a data set with various permission levels as appropriate.

The data, including the header or trailer may be received by a standalone interaction device configured to add, delete, modify, or augment the data in accordance with the header or trailer. As such, in one embodiment, the header or trailer is not stored on the transaction device along with the associated issuer-owned data but instead the appropriate action may be taken by providing to the user at the standalone device, the appropriate option for the action to be taken. The system may contemplate a data storage arrangement wherein the header or trailer, or header or trailer history, of the data is stored on the system, device or transaction account in relation to the appropriate data.

One skilled in the art will also appreciate that, for security reasons, any databases, systems, devices, servers or other components of the system may consist of any combination thereof at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, and/or the like.

Encryption may be performed by way of any of the techniques now available in the art or which may become available—e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI, GPG (GnuPG), and symmetric and asymmetric cryptosystems.

The computing unit of the web client may be further equipped with an Internet browser connected to the Internet or an intranet using standard dial-up, cable, DSL or any other Internet protocol known in the art. Transactions originating at a web client may pass through a firewall in order to prevent unauthorized access from users of other networks. Further, additional firewalls may be deployed between the varying components of CMS to further enhance security.

Firewall may include any hardware and/or software suitably configured to protect CMS components and/or enterprise computing resources from users of other networks. Further, a firewall may be configured to limit or restrict access to various systems and components behind the firewall for web clients connecting through a web server. Firewall may reside in varying configurations including Stateful Inspection, Proxy based, access control lists, and Packet Filtering among others. Firewall may be integrated within a web server or any other CMS components or may further reside as a separate entity. A firewall may implement network address translation (“NAT”) and/or network address port translation (“NAPT”). A firewall may accommodate various tunneling protocols to facilitate secure communications, such as those used in virtual private networking. A firewall may implement a demilitarized zone (“DMZ”) to facilitate communications with a public network such as the Internet. A firewall may be integrated as software within an Internet server, any other application server components or may reside within another computing device or may take the form of a standalone hardware component.

The computers discussed herein may provide a suitable website or other Internet-based graphical user interface which is accessible by users. In one embodiment, the MICROSOFT® INTERNET INFORMATION SERVICES® (IIS), MICROSOFT® Transaction Server (MTS), and MICROSOFT® SQL Server, are used in conjunction with the MICROSOFT® operating system, MICROSOFT® NT web server software, a MICROSOFT® SQL Server database system, and a MICROSOFT® Commerce Server. Additionally, components such as Access or MICROSOFT® SQL Server, ORACLE®, Sybase, Informix MySQL, Interbase, etc., may be used to provide an Active Data Object (ADO) compliant database management system. In one embodiment, the Apache web server is used in conjunction with a Linux operating system, a My SQL database, and the Perl, PHP, and/or Python programming languages.

Any of the communications, inputs, storage, databases or displays discussed herein may be facilitated through a website having web pages. The term “web page” as it is used herein is not meant to limit the type of documents and applications that might be used to interact with the user. For example, a typical website might include, in addition to standard HTML documents, various forms, JAVA® APPLE®ts, JAVASCRIPT, active server pages (ASP), common gateway interface scripts (CGI), extensible markup language (XML), dynamic HTML, cascading style sheets (CSS), AJAX (Asynchronous JAVASCRIPT And XML), helper applications, plug-ins, and the like. A server may include a web service that receives a request from a web server, the request including a URL and an IP address (123.56.789.234). The web server retrieves the appropriate web pages and sends the data or applications for the web pages to the IP address. Web services are applications that are capable of interacting with other applications over a communications means, such as the internet. Web services are typically based on standards or protocols such as XML, SOAP, AJAX, WSDL and UDDI. Web services methods are well known in the art, and are covered in many standard texts. See, e.g., ALEX NGHIEM, IT WEB SERVICES: A ROADMAP FOR THE ENTERPRISE (2003), hereby incorporated by reference.

Middleware may include any hardware and/or software suitably configured to facilitate communications and/or process transactions between disparate computing systems. Middleware components are commercially available and known in the art. Middleware may be implemented through commercially available hardware and/or software, through custom hardware and/or software components, or through a combination thereof. Middleware may reside in a variety of configurations and may exist as a standalone system or may be a software component residing on the Internet server. Middleware may be configured to process transactions between the various components of an application server and any number of internal or external systems for any of the purposes disclosed herein. WEBSPHERE MQ™ (formerly MQSeries) by IBM®, Inc. (Armonk, N.Y.) is an example of a commercially available middleware product. An Enterprise Service Bus (“ESB”) application is another example of middleware.

Practitioners will also appreciate that there are a number of methods for displaying data within a browser-based document. Data may be represented as standard text or within a fixed list, scrollable list, drop-down list, editable text field, fixed text field, pop-up window, and the like. Likewise, there are a number of methods available for modifying data in a web page such as, for example, free text entry using a keyboard, selection of menu items, check boxes, option boxes, and the like.

The systems and methods may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the system may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the system may be implemented with any programming or scripting language such as C, C++, C#, JAVA®, JAVASCRIPT, VBScript, Macromedia Cold Fusion, COBOL, MICROSOFT® Active Server Pages, assembly, PERL, PHP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, any UNIX shell script, and extensible markup language (XML) with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the system may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. Still further, the system could be used to detect or prevent security issues with a client-side scripting language, such as JAVASCRIPT, VBScript or the like. For a basic introduction of cryptography and network security, see any of the following references: (1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,” by Bruce Schneier, published by John Wiley & Sons (second edition, 1995); (2) “JAVA® Cryptography” by Jonathan Knudson, published by O'Reilly & Associates (1998); (3) “Cryptography & Network Security: Principles & Practice” by William Stallings, published by Prentice Hall; all of which are hereby incorporated by reference.

As used herein, the term “user”, “consumer”, “customer”, “cardmember”, “business” or “merchant” may be used interchangeably with each other, and each shall mean any person, entity, government organization, business, machine, hardware, and/or software. A bank (e.g., the issuer) may be part of the system, but the bank may represent other types of card issuing institutions, such as credit card companies, card sponsoring companies, or third party issuers under contract with financial institutions. It is further noted that other participants may be involved in some phases of the transaction, such as an intermediary settlement institution, but these participants are not shown.

Each participant is equipped with a computing device in order to interact with the system and facilitate online commerce transactions. The user has a computing unit in the form of a personal computer, although other types of computing units may be used including laptops, notebooks, hand held computers, set-top boxes, cellular telephones, touch-tone telephones and the like. The merchant has a computing unit implemented in the form of a computer-server, although other implementations are contemplated by the system. The bank has a computing center shown as a main frame computer. However, the bank computing center may be implemented in other forms, such as a mini-computer, a PC server, a network of computers located in the same of different geographic locations, or the like. Moreover, the system contemplates the use, sale or distribution of any goods, services or information over any network having similar functionality described herein

The merchant computer and/or server and the bank computer and/or server may be interconnected via a second network, referred to as a payment network. The payment network which may be part of certain transactions represents existing proprietary networks that presently accommodate transactions for credit cards, debit cards, and other types of financial/banking cards. The payment network is a closed network that is assumed to be secure from eavesdroppers. Exemplary transaction networks may include the American Express®, VisaNet® and the Veriphone® networks.

The electronic commerce system may be implemented at the customer and issuing bank. In an exemplary implementation, the electronic commerce system is implemented as computer software modules loaded onto the customer computer and the banking computing center. The merchant computer does not require any additional software to participate in the online commerce transactions supported by the online commerce system.

As will be appreciated by one of ordinary skill in the art, the system may be embodied as a customization of an existing system, an add-on product, a processing apparatus executing upgraded software, a stand alone system, a distributed system, a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, any portion of the system or a module may take the form of a processing apparatus executing code, an internet based embodiment, an entirely hardware embodiment, or an embodiment combining aspects of the internet, software and hardware. Furthermore, the system may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, optical storage devices, magnetic storage devices, and/or the like.

The system and method is described herein with reference to screen shots, block diagrams and flowchart illustrations of methods, apparatus (e.g., systems), and computer program products according to various embodiments. It will be understood that each functional block of the block diagrams and the flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by computer program instructions.

These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions that execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each functional block of the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, can be implemented by either special purpose hardware-based computer systems which perform the specified functions or steps, or suitable combinations of special purpose hardware and computer instructions. Further, illustrations of the process flows and the descriptions thereof may make reference to user WINDOWS®, webpages, websites, web forms, prompts, etc. Practitioners will appreciate that the illustrated steps described herein may comprise in any number of configurations including the use of WINDOWS®, webpages, web forms, popup WINDOWS®, prompts and the like. It should be further appreciated that the multiple steps as illustrated and described may be combined into single webpages and/or WINDOWS® but have been expanded for the sake of simplicity. In other cases, steps illustrated and described as single process steps may be separated into multiple webpages and/or WINDOWS® but have been combined for simplicity.

The term “non-transitory” is to be understood to remove only propagating transitory signals per se from the claim scope and does not relinquish rights to all standard computer-readable media that are not only propagating transitory signals per se. Stated another way, the meaning of the term “non-transitory computer-readable medium” and “non-transitory computer-readable storage medium” should be construed to exclude only those types of transitory computer-readable media which were found in In Re Nuijten to fall outside the scope of patentable subject matter under 35 U.S.C. §101.

In yet another embodiment, the transponder, transponder-reader, and/or transponder-reader system are configured with a biometric security system that may be used for providing biometrics as a secondary form of identification. The biometric security system may include a transponder and a reader communicating with the system. The biometric security system also may include a biometric sensor that detects biometric samples and a device for verifying biometric samples. The biometric security system may be configured with one or more biometric scanners, processors and/or systems. A biometric system may include one or more technologies, or any portion thereof, such as, for example, recognition of a biometric. As used herein, a biometric may include a user's voice, fingerprint, facial, ear, signature, vascular patterns, DNA sampling, hand geometry, sound, olfactory, keystroke/typing, iris, retinal or any other biometric relating to recognition based upon any body part, function, system, attribute and/or other characteristic, or any portion thereof.

Phrases and terms similar to an “party” may include any individual, consumer, customer, group, business, organization, government entity, transaction account issuer or processor (e.g., credit, charge, etc), merchant, consortium of merchants, account holder, charitable organization, software, hardware, and/or any other type of entity. The terms “user,” “consumer,” “purchaser,” and/or the plural form of these terms are used interchangeably throughout herein to refer to those persons or entities that are alleged to be authorized to use a transaction account.

Phrases and terms similar to “account”, “account number”, “account code”, “consumer account”, or “consumer credential” as used herein, may include any device, code (e.g., one or more of an authorization/access code, personal identification number (“PIN”), Internet code, other identification code, and/or the like), number, letter, symbol, digital certificate, smart chip, digital signal, analog signal, biometric or other identifier/indicia suitably configured to allow the consumer to access, interact with or communicate with the system. The account number may optionally be located on or associated with a rewards account, charge account, credit account, debit account, prepaid account, telephone card, embossed card, smart card, magnetic stripe card, bar code card, transponder, radio frequency card or an associated account.

The system may include or interface with any of the foregoing accounts, devices, and/or a transponder and reader (e.g. RFID reader) in RF communication with the transponder (which may include a fob), or communications between an initiator and a target enabled by near field communications (NFC). Typical devices may include, for example, a key ring, tag, card, cell phone, wristwatch or any such form capable of being presented for interrogation. Moreover, the system, computing unit or device discussed herein may include a “pervasive computing device,” which may include a traditionally non-computerized device that is embedded with a computing unit. Examples may include watches, Internet enabled kitchen appliances, restaurant tables embedded with RF readers, wallets or purses with imbedded transponders, etc. Furthermore, a device or financial transaction account may have electronic and communications functionality enabled, for example, by: a network of electronic circuitry that is printed or otherwise incorporated onto or within the transaction account (and typically referred to as a “smart card”); a fob having a transponder and an RFID reader; and/or near field communication (NFC) technologies. For more information regarding NFC, refer to the following specifications all of which are incorporated by reference herein: ISO/IEC 18092/ECMA-340, Near Field Communication Interface and Protocol-1 (NFCIP-1); ISO/IEC 21481/ECMA-352, Near Field Communication Interface and Protocol-2 (NFCIP-2); and EMV 4.2 available at http:ww.emvco.com/default.aspx.

The account number may be distributed and stored in any form of plastic, electronic, magnetic, radio frequency, wireless, audio and/or optical device capable of transmitting or downloading data from itself to a second device. A consumer account number may be, for example, a sixteen-digit account number, although each credit provider has its own numbering system, such as the fifteen-digit numbering system used by American Express. Each company's account numbers comply with that company's standardized format such that the company using a fifteen-digit format will generally use three-spaced sets of numbers, as represented by the number “0000 000000 00000”. The first five to seven digits are reserved for processing purposes and identify the issuing bank, account type, etc. In this example, the last (fifteenth) digit is used as a sum check for the fifteen digit number. The intermediary eight-to-eleven digits are used to uniquely identify the consumer. A merchant account number may be, for example, any number or alpha-numeric characters that identify a particular merchant for purposes of account acceptance, account reconciliation, reporting, or the like.

In various embodiments, an account number may identify a consumer. In addition, in various embodiments, a consumer may be identified by a variety of identifiers, including, for example, an email address, a telephone number, a cookie id, a radio frequency identifier (RFID), a biometric, and the like.

Phrases and terms similar to “transaction account” may include any account that may be used to facilitate a financial transaction.

Phrases and terms similar to “financial institution” or “transaction account issuer” may include any entity that offers transaction account services. Although often referred to as a “financial institution,” the financial institution may represent any type of bank, lender or other type of account issuing institution, such as credit card companies, card sponsoring companies, or third party issuers under contract with financial institutions. It is further noted that other participants may be involved in some phases of the transaction, such as an intermediary settlement institution.

Phrases and terms similar to “business” or “merchant” may be used interchangeably with each other and shall mean any person, entity, distributor system, software and/or hardware that is a provider, broker and/or any other entity in the distribution chain of goods or services. For example, a merchant may be a grocery store, a retail store, a travel agency, a service provider, an on-line merchant or the like.

The terms “payment vehicle,” “financial transaction account,” “transaction account” and/or the plural form of these terms may be used interchangeably throughout to refer to a financial instrument.

Phrases and terms similar to “merchant,” “supplier” or “seller” may include any entity that receives payment or other consideration. For example, a supplier may request payment for goods sold to a buyer who holds an account with a transaction account issuer.

Phrases and terms similar to a “buyer” may include any entity that receives goods or services in exchange for consideration (e.g. financial payment). For example, a buyer may purchase, lease, rent, barter or otherwise obtain goods from a supplier and pay the supplier using a transaction account.

Phrases and terms similar to “internal data” may include any data a credit issuer possesses or acquires pertaining to a particular consumer. Internal data may be gathered before, during, or after a relationship between the credit issuer and the transaction account holder (e.g., the user, consumer or buyer). Such data may include consumer demographic data. Consumer demographic data includes any data pertaining to a consumer. Consumer demographic data may include consumer name, address, telephone number, email address, employer and social security number. Consumer transactional data is any data pertaining to the particular transactions in which a consumer engages during any given time period. Consumer transactional data may include, for example, transaction amount, transaction time, transaction vendor/merchant, and transaction vendor/merchant location. Transaction vendor/merchant location may contain a high degree of specificity to a vendor/merchant. For example, transaction vendor/merchant location may include a particular gasoline filing station in a particular postal code located at a particular cross section or address. Also, for example, transaction vendor/merchant location may include a particular web address, such as a Uniform Resource Locator (“URL”), an email address and/or an Internet Protocol (“IP”) address for a vendor/merchant. Transaction vendor/merchant, and transaction vendor/merchant location may be associated with a particular consumer and further associated with sets of consumers. Consumer payment data includes any data pertaining to a consumer's history of paying debt obligations. Consumer payment data may include consumer payment dates, payment amounts, balance amount, and credit limit. Internal data may further comprise records of consumer service calls, complaints, requests for credit line increases, questions, and comments. A record of a consumer service call includes, for example, date of call, reason for call, and any transcript or summary of the actual call.

Phrases similar to a “payment processor” or “payment service provider” may include a company (e.g., a third party) appointed (e.g., by a merchant) to handle transactions. A payment processor may include an issuer, acquirer, authorizer and/or any other system or entity involved in the transaction process. Payment processors may be broken down into two types: front-end and back-end. Front-end payment processors have connections to various transaction accounts and supply authorization and settlement services to the merchant banks' merchants. Back-end payment processors accept settlements from front-end payment processors and, via The Federal Reserve Bank, move money from an issuing bank to the merchant bank. In an operation that will usually take a few seconds, the payment processor will both check the details received by forwarding the details to the respective account's issuing bank or card association for verification, and may carry out a series of anti-fraud measures against the transaction. Additional parameters, including the account's country of issue and its previous payment history, may be used to gauge the probability of the transaction being approved. In response to the payment processor receiving confirmation that the transaction account details have been verified, the information may be relayed back to the merchant, who will then complete the payment transaction. In response to the verification being denied, the payment processor relays the information to the merchant, who may then decline the transaction.

Phrases similar to a “payment gateway” or “gateway” may include an application service provider service that authorizes payments for e-businesses, online retailers, and/or traditional brick and mortar merchants. The gateway may be the equivalent of a physical point of sale terminal located in most retail outlets. A payment gateway may protect transaction account details by encrypting sensitive information, such as transaction account numbers, to ensure that information passes securely between the customer and the merchant and also between merchant and payment processor.

Benefits, other advantages, and solutions to problems have been described herein with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any elements that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of the disclosure. The scope of the disclosure is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more.” Moreover, where a phrase similar to ‘at least one of A, B, and C’ or ‘at least one of A, B, or C’ is used in the claims or specification, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C. Although the disclosure includes a method, it is contemplated that it may be embodied as computer program instructions on a tangible computer-readable carrier, such as a magnetic or optical memory or a magnetic or optical disk. All structural, chemical, and functional equivalents to the elements of the above-described various embodiments that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. Moreover, it is not necessary for a device or method to address each and every problem sought to be solved by the present disclosure, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. No claim element herein is to be construed under the provisions of 35 U.S.C. 112 (f) unless the element is expressly recited using the phrase “means for.” As used herein, the terms “comprises”, “comprising”, or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. 

What is claimed is:
 1. A method, comprising: transmitting, by a computer based system, wallet provider script to a payment service provider server, wherein the payment service provider server is configured to integrate the wallet provider script; presenting, by the computer based system, an electronic wallet payment tool on a merchant checkout page in response to the transmitting the wallet provider script, wherein the merchant checkout page is part of a merchant server belonging to a merchant, wherein the payment service provider server is integrated with the merchant server; receiving, by the computer based system, a first selection of the electronic wallet payment tool by a consumer to complete a transaction; retrieving, by the computer based system, an electronic wallet comprised in a transaction account associated with the consumer in response to the receiving the first selection, wherein the electronic wallet comprises transaction account information associated with the consumer; transmitting, by the computer based system, the transaction account information associated with a desired transaction account to the payment service provider server; receiving, by the computer based system, a virtual token from the payment service provider server in response to the transmitting the transaction account information; and transmitting, by the computer based system, the virtual token to payment service provider script integrated in a browser used by the consumer, wherein the payment service provider script is configured to receive the virtual token and provide the virtual token to the merchant server.
 2. The method of claim 1, further comprising presenting, by the computer based system, a login tool in response to the receiving the first selection of the electronic wallet payment tool.
 3. The method of claim 2, further comprising receiving, by the computer based system, a consumer credential provided by the consumer through the login tool.
 4. The method of claim 3, further comprising authenticating, by the computer based system, the consumer associated with the transaction account in response to the receiving the consumer credential.
 5. The method of claim 1, further comprising receiving, by the computer based system, merchant information associated with the merchant.
 6. The method of claim 1, further comprising presenting, by the computer based system, a transaction account selection tool, wherein the transaction account information comprises information for a plurality of transaction accounts.
 7. The method of claim 6, further comprising receiving, by the computer based system, a second selection of the desired transaction account from the plurality of transaction accounts.
 8. An article of manufacture including a non-transitory, tangible computer readable memory having instructions stored thereon that, in response to execution by a computer based system, cause the computer based system to perform operations comprising: transmitting, by the computer based system, wallet provider script to a payment service provider server, wherein the payment service provider server is configured to integrate the wallet provider script; presenting, by the computer based system, an electronic wallet payment tool on a merchant checkout page in response to the transmitting the wallet provider script, wherein the merchant checkout page is part of a merchant server belonging to a merchant, wherein the payment service provider server is integrated with the merchant server; receiving, by the computer based system, a first selection of the electronic wallet payment tool by a consumer to complete a transaction; retrieving, by the computer based system, an electronic wallet comprised in a transaction account associated with the consumer in response to the receiving the first selection, wherein the electronic wallet comprises transaction account information associated with the consumer; transmitting, by the computer based system, the transaction account information associated with a desired transaction account to the payment service provider server; receiving, by the computer based system, a virtual token from the payment service provider in response to the transmitting the transaction account information; and transmitting, by the computer based system, the virtual token to payment service provider script integrated in a browser used by the consumer, wherein the payment service provider script is configured to receive the virtual token and provide the virtual token to the merchant server.
 9. The article of claim 8, wherein the operations further comprise presenting, by the computer based system, a login tool in response to the receiving the first selection of the electronic wallet payment tool.
 10. The article of claim 9, wherein the operations further comprise receiving, by the computer based system, a consumer credential provided by the consumer through the login tool.
 11. The article of claim 10, wherein the operations further comprise authenticating, by the computer based system, the consumer associated with the transaction account in response to the receiving the consumer credential.
 12. The article of claim 8, wherein the operations further comprise receiving, by the computer based system, merchant information associated with the merchant.
 13. The article of claim 8, wherein the operations further comprise presenting, by the computer based system, a transaction account selection tool, wherein the transaction account information comprises information for a plurality of transaction accounts.
 14. The article of claim 13, wherein the operations further comprise receiving, by the computer based system, a second selection of the desired transaction account from the plurality of transaction accounts.
 15. A computer based system comprising: a processor; and a tangible, non-transitory memory configured to communicate with the processor, the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the processor to perform operations comprising: transmitting, by the computer based system, wallet provider script to a payment service provider server, wherein the payment service provider server is configured to integrate the wallet provider script; presenting, by the computer based system, an electronic wallet payment tool on a merchant checkout page in response to the transmitting the wallet provider script, wherein the merchant checkout page is part of a merchant server belonging to a merchant, wherein the payment service provider server is integrated with the merchant server; receiving, by the computer based system, a first selection of the electronic wallet payment tool by a consumer to complete a transaction; retrieving, by the computer based system, an electronic wallet comprised in a transaction account associated with the consumer in response to the receiving the first selection, wherein the electronic wallet comprises transaction account information associated with the consumer; transmitting, by the computer based system, the transaction account information associated with a desired transaction account to the payment service provider server; receiving, by the computer based system, a virtual token from the payment service provider in response to the transmitting the transaction account information; and transmitting, by the computer based system, the virtual token to payment service provider script integrated in a browser used by the consumer, wherein the payment service provider script is configured to receive the virtual token and provide the virtual token to the merchant server.
 16. The system of claim 15, further comprising presenting, by the computer based system, a login tool in response to the receiving the first selection of the electronic wallet payment tool.
 17. The system of claim 16, further comprising receiving, by the computer based system, a consumer credential provided by the consumer through the login tool.
 18. The system of claim 17, further comprising authenticating, by the computer based system, the consumer associated with the transaction account in response to the receiving the consumer credential.
 19. The system of claim 15, further comprising presenting, by the computer based system, a transaction account selection tool, wherein the transaction account information comprises information for a plurality of transaction accounts.
 20. The system of claim 19, further comprising receiving, by the computer based system, a second selection of the desired transaction account from the plurality of transaction accounts. 